The free-threaded build's GC implementation is non-generational, but was scheduled as if it were collecting a young generation leading to quadratic behavior. This increases the minimum threshold and scales it to the number of live objects as we do for the old generation in the default build.

Note that the scheduling is still not thread-safe without the GIL. Those changes will come in later PRs.

A few tests, like "test_sneaky_frame_object" rely on prompt scheduling of the GC. For now, to keep that test passing, we disable the scaled threshold after calls like gc.set_threshold(1, 0, 0).

• Issue: test_pendingcalls_threaded times out on Windows free-threading builds #114746